Methods and nodes for determining a transmission data block size

ABSTRACT

A method in a User Equipment (UE) for determining a transmission data block size is provided. The method comprises: obtaining parameters for a data transmission, the parameters including at least a number of layers, a number of allocated resource blocks, a modulation order and a code rate; determining an effective number of resource elements; determining a transmission data block size based on the obtained parameters and the determined effective number of resource elements; and performing one of transmitting and receiving data based on the determined transmission data block size.

RELATED APPLICATIONS

The present application claims the benefits of priority of U.S.Provisional Patent Application No. 62/473,839, entitled “TransmissionData Block Size Determination”, and filed at the United States Patentand Trademark Office on Mar. 20, 2017, the content of which isincorporated herein by reference.

TECHNICAL FIELD

The present description generally relates to wireless communicationsystems and, in particular, to determining transmission data block sizewithin such systems.

BACKGROUND

In 3GPP (Third Generation Partnership Project), there are studies on newprotocols collectively referred to as new radio (NR) interface for 5G.Various terms are used in the art for this new and next generationtechnology. The terms NR and 5G are used in the present disclosureinterchangeably. Moreover, a base-station can be referred to as gNBinstead of eNB. Alternatively, the term Transmission-Receive-point (TRP)can also be used.

Slot Structure

An NR slot consists of several Orthogonal Frequency DivisionMultiplexing (OFDM) symbols, according to current agreements either 7 or14 symbols per slot (for OFDM subcarrier spacing ≤60 kHz) or 14 symbolsper slot (for OFDM subcarrier spacing >60 kHz). FIG. 1a shows a subframewith 14 OFDM symbols as an example. In FIG. 1a , T_(s) and T_(symb)denote the slot and OFDM symbol duration, respectively.

In addition, a slot may also be shortened to accommodate Downlink/Uplink(DL/UL) transient period or both DL and UL transmissions. Potential slotvariations are shown in FIG. 1b . For example, FIG. 1b shows, from topto bottom, a slot with DL-only transmission with a late start, a slotwith DL-heavy transmission with UL part, a slot with UL-heavytransmission with DL control and a slot with UL-only transmission.

Furthermore, NR also defines mini-slots. Mini-slots are shorter in timethan slots (according to current agreements from 1 or 2 symbols up tothe number of symbols in a slot minus one) and can start at any symbol.Mini-slots are used if the transmission duration of a slot is too longor the occurrence of the next slot start (slot alignment) is too late.Applications of mini-slots include, among others, latency criticaltransmissions (in this case both mini-slot length and frequentopportunity of mini-slot are important) and unlicensed spectrum where atransmission should start immediately after listen-before-talk succeeded(here the frequent opportunity of mini-slot is especially important). Anexample of mini-slots is shown in FIG. 1c (the exemplary mini slots arethe OFDM symbols shown in FIG. 1c ).

Control Information

PDCCHs (physical downlink control channels) are used in NR for downlinkcontrol information (DCI), e.g. downlink scheduling assignments anduplink scheduling grants. The PDCCHs are in general transmitted at thebeginning of a slot and relate to data in the same or a later slot (formini-slots PDCCH can also be transmitted within a regular slot).Different formats (sizes) of the PDCCHs are possible to handle differentDCI payload sizes and different aggregation levels (i.e. different coderate for a given payload size). A UE is configured (implicitly and/orexplicitly) to monitor (or search) for a number of PDCCH candidates ofdifferent aggregation levels and DCI payload sizes. Upon detecting avalid DCI message (i.e. the decoding of a candidate is successful andthe DCI contains an Identity (ID) the UE is told to monitor) the UEfollows the DCI (e.g. receives the corresponding downlink data ortransmits in the uplink).

In NR concept discussions, the introduction of a ‘broadcasted controlchannel’ to be received by multiple UEs is considered. Such a channelhas been referred to as ‘group common PDCCH’. The exact content of sucha channel is under discussion. One example of information that might beput in such a channel is information about the slot format, i.e. whethera certain slot is uplink or downlink, which portion of a slot is UL orDL; such information which could be useful, for example, in a dynamicTDD (Time Division Duplex) system.

Transmission Parameter Determination

In the Long Term Evolution (LTE) existent protocols, the downlinkcontrol information (DCI) carries several parameters to instruct the UEhow to receive the downlink transmission or to transmit in the uplink.For example, the Frequency Division Duplex (FDD) LTE DCI format 1Acarries parameter such as Localized/Distributed Virtual Resource Block(VRB) assignment flag, Resource block assignment, Modulation and codingscheme (MCS), HARQ process number, New data indicator, Redundancyversion and TPC (Transmit Power Control) command for PUCCH (PhysicalUplink Control Channel).

One of the key parameters for the UE to be able to receive or transmitin the system is the size of the data block (called transport block size(TBS)) to be channel coded and modulated. In LTE, this is determined asfollows:

-   -   The UE uses Modulation and coding scheme given by the DCI to        read a transport block size (TBS) index I_(TBS) from a        modulation and coding scheme (MCS) table. An example of the MCS        table is shown in Table 1.    -   The UE determines the number of physical radio blocks (PRBs) as        N_(PRB) from the Resource block assignment given in the DCI.    -   The UE uses the TBS index I_(TBS) and the number of PRBs N_(PRB)        to read the actual transport block size from a TBS table. A        portion of the TBS table is shown in Table 2 as an example.

TABLE 1 LTE modulation and coding scheme (MCS) table MCS Modulation TBSIndex Order Index I_(MCS) Q_(m) I_(TBS) 0 2 0 1 2 1 2 2 2 3 2 3 4 2 4 52 5 6 2 6 7 2 7 8 2 8 9 2 9 10 4 9 11 4 10 12 4 11 13 4 12 14 4 13 15 414 16 4 15 17 6 15 18 6 16 19 6 17 20 6 18 21 6 19 22 6 20 23 6 21 24 622 25 6 23 26 6 24 27 6 25 28 6 26 29 2 reserved 30 4 31 6

TABLE 2 LTE transport block size (TBS) table (dimension is 27 × 110)N_(PRB) I_(TBS) 1 2 3 4 5 6 7 8 9 . . . 0 16 32 56 88 120 152 176 208224 . . . 1 24 56 88 144 176 208 224 256 328 . . . 2 32 72 144 176 208256 296 328 376 . . . 3 40 104 176 208 256 328 392 440 504 . . . 4 56120 208 256 328 408 488 552 632 . . . 5 72 144 224 328 424 504 600 680776 . . . 6 328 176 256 392 504 600 712 808 936 . . . 7 104 224 328 472584 712 840 968 1096 . . . 8 120 256 392 536 680 808 968 1096 1256 . . .9 136 296 456 616 776 936 1096 1256 1416 . . . 10 144 328 504 680 8721032 1224 1384 1544 . . . 11 176 376 584 776 1000 1192 1384 1608 1800 .. . 12 208 440 680 904 1128 1352 1608 1800 2024 . . . 13 224 488 7441000 1256 1544 1800 2024 2280 . . . 14 256 552 840 1128 1416 1736 19922280 2600 . . . 15 280 600 904 1224 1544 1800 2152 2472 2728 . . . 16328 632 968 1288 1608 1928 2280 2600 2984 . . . 17 336 696 1064 14161800 2152 2536 2856 3240 . . . 18 376 776 1160 1544 1992 2344 2792 31123624 . . . 19 408 840 1288 1736 2152 2600 2984 3496 3880 . . . 20 440904 1384 1864 2344 2792 3240 3752 4136 . . . 21 488 1000 1480 1992 24722984 3496 4008 4584 . . . 22 520 1064 1608 2152 2664 3240 3752 4264 4776. . . 23 552 1128 1736 2280 2856 3496 4008 4584 5160 . . . 24 584 11921800 2408 2984 3624 4264 4968 5544 . . . 25 616 1256 1864 2536 3112 37524392 5160 5736 . . . 26 712 1480 2216 2984 3752 4392 5160 5992 6712 . ..

Problems with the Existent LTE Approach Problem 1

The LTE TBS table was originally designed with specific assumptions onthe number of resource elements (REs) available within each allocatedPRB as well as the number of OFDM symbols for data transmissions. Whendifferent transmission modes with different amount of reference symboloverheads were introduced later in LTE, it became difficult to defineanother TBS table to optimize for the new transmission modes. A few newrows were introduced in the LTE TBS table to optimize for a few limitedcases. It can be seen that the explicit TBS table approach hinderscontinual evolution and improvement of the LTE system.

Problem 2

The existing approach of determining the data block size does notprovide high performance operation with different slot sizes orstructures. This is a problem in LTE system since a subframe in LTE maybe of various sizes. A regular subframe may have different sizes ofcontrol region and thus leaves different sizes for the data region. TDDLTE supports special subframes of different sizes in the Downlink partof the Special Subframe (DwPTS). Various different sizes of subframe aresummarized in Table 3.

However, the LTE MCS and TBS tables are designed based on the assumptionthat 11 OFDM symbols are available for the data transmission. That is,when the actual number of available OFDM symbols for PDSCH (PhysicalDownlink Shared Channel) is different than 11, the spectral efficiencyof the transmission will deviate from those shown in Table 4. First, thecode rate becomes excessively high when the actual number of OFDMsymbols for PDSCH is substantially less than the assumed 11 symbols.These cases are highlighted with dark shades in Table 4. Currently inLTE, the UE is not expected to decode any PDSCH transmission witheffective code rate higher than 0.930. Since the mobile station will notbe able to decode such high code rates, transmissions based on thesedark shaded MCSs will fail and retransmissions will be needed. Secondly,with the mismatch of radio resource assumption, code rates for some ofthe MCSs deviate out of the optimal range for the wideband wirelesssystem. Based on extensive link performance evaluation for the downlinktransmission as an example, the code rates for QPSK (Quadrature PhaseShift Keying) and 16 QAM (Quadrature Amplitude Modulation) should not behigher than 0.70. Furthermore, the code rates for 16 QAM and 64 QAMshould not be lower than 0.32 and 0.40, respectively. As illustratedwith light shades, some of the MCSs in Table 4 result in sub-optimalcode rates.

Since data throughput is reduced when transmissions are based onunsuitable sub-optimal code rates, a good scheduling implementation inthe base station should avoid using any shaded MCSs shown in Table 4. Itcan be concluded that the number of usable MCSs shrink significantlywhen the actual number of OFDM symbols for PDSCH deviates from theassumed 11 symbols.

TABLE 3 Available number of OFDM symbols for PDSCH (N_(OS)) in LTENumber of OFDM symbols for control information Operation mode 1 2 3 4FDD, TDD Normal CP 13 12 11 10 Extended CP 11 10 9 8 TDD DwPTSconfigurations 1, 6 8 7 6 5 normal CP configurations 2, 7 9 8 7 6configurations 3, 8 10 9 8 7 configuration 4 11 10 9 8 TDD DwPTSconfigurations 1, 5 7 6 5 4 extended CP configurations 2, 6 8 7 6 5configuration 3 9 8 7 6

Problem 3

As mentioned in the above section on Slot Structure, the slot structurefor NR tends to be more flexible with much larger range of the amount ofallocated resource for the UE to receive or transmit. The base ofdesigning a TBS table (as stated earlier on the specific assumption onthe number of resource elements (REs) available within each allocatedPRB as well as the number of OFDM symbols for data transmissions)diminishes significantly.

SUMMARY

Some embodiments of the present disclosure provide methods, nodes andcomputer programs to determine a transmission data block size (TDBS)that may address some or all of the above noted problems, and/or mayallow an easier evolution or changes of a radio access system and/or mayallow improved performance of a radio access network. According to someembodiments of the present disclosure, the transmission data block sizecan be determined by an Modulation Coding Scheme (MCS) index and aneffective number of Resource Elements (REs) per allocated PhysicalResource Block (PRB).

According to one aspect, some embodiments include a method performed bya user equipment for determining a transmission data block size. Themethod generally comprises obtaining parameters for a data transmission,the parameters including at least a number of layers, a number ofallocated resource blocks, a modulation order and a code rate;determining an effective number of resource elements; determining atransmission data block size (TDBS) based on the obtained parameters andthe determined effective number of resource elements; and performing oneof transmitting and receiving data based on the determined transmissiondata block size.

According to another aspect, some embodiments include a user equipmentconfigured, or operable, to perform one or more functionalities (e.g.actions, operations, steps, etc.) as described herein.

In some embodiments, the user equipment may comprise a processingcircuitry configured to: obtain parameters for a data transmission, theparameters including at least a number of layers, a number of allocatedresource blocks, a modulation order and a code rate; determine aneffective number of resource elements; determine a transmission datablock size (TDBS) based on the obtained parameters and the determinedeffective number of resource elements; and perform one of transmit andreceive data based on the determined transmission data block size.

In some embodiments, the user equipment (UE) may comprise one or morefunctional modules configured to perform one or more functionalities ofthe UE as described herein.

According to another aspect, some embodiments include a non-transitorycomputer-readable medium storing a computer program product comprisinginstructions which, upon being executed by a processing circuitry (e.g.,at least one processor) of the UE, configure the processing circuitry toperform one or more UE functionalities as described herein.

According to another aspect, there is provided a method for transmittingor receiving data. The method comprises: transmitting parameters for adata transmission, the parameters including at least a number of layers,a number of allocated resource blocks, a modulation order and a coderate; transmitting an effective number of resource elements; andperforming one of receiving and transmitting data based on atransmission data block size, which is determined based on thetransmitted parameters and effective number of resource elements.

Yet, according to another aspect, there is provided a network node fortransmitting or receiving data. The network node comprises a processingcircuitry configured to: transmit parameters for a data transmission,the parameters including a number of layers, a number of allocatedresource blocks, a modulation order and a code rate; transmit aneffective number of resource elements; and perform one of receive andtransmit data based on a transmission data block size, which isdetermined based on the transmitted parameters and effective number ofresource elements.

This summary is not an extensive overview of all contemplatedembodiments and is not intended to identify key or critical aspects orfeatures of any or all embodiments or to delineate the scope of any orall embodiments. In that sense, other aspects and features will becomeapparent to those ordinarily skilled in the art upon review of thefollowing description of specific embodiments in conjunction with theaccompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments will be described in more detail with reference tothe following figures, in which:

FIGS. 1a, 1b and 1c illustrate examples of a slot, slot variations and amini-slot according to an NR system.

FIG. 2 illustrates one example of a wireless communications system inwhich embodiments of the present disclosure may be implemented.

FIG. 3 is a flow chart that illustrates the operation of a radio nodeaccording to some embodiments of the present disclosure.

FIG. 4 is a flow chart that illustrates the operation of a radio nodeaccording to other embodiments of the present disclosure.

FIGS. 5 and 6 are block diagrams that illustrate a wireless deviceaccording to some embodiments of the present disclosure.

FIGS. 7 through 9 are block diagrams that illustrate a radio access nodeaccording to some embodiments of the present disclosure.

FIG. 10 illustrates a flow chart of a method in a user equipment (UE)according to some embodiments.

FIG. 11 illustrates a flow chart of a method in a network node inaccordance with some embodiments.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable thoseskilled in the art to practice the embodiments. Upon reading thefollowing description in light of the accompanying figures, thoseskilled in the art will understand the concepts of the description andwill recognize applications of these concepts not particularly addressedherein. It should be understood that these concepts and applicationsfall within the scope of the description.

In the following description, numerous specific details are set forth.However, it is understood that embodiments may be practiced withoutthese specific details. In other instances, well-known circuits,structures, and techniques have not been shown in detail in order not toobscure the understanding of the description. Those of ordinary skill inthe art, with the included description, will be able to implementappropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to implement such feature, structure, orcharacteristic in connection with other embodiments whether or notexplicitly described.

As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises,”“comprising,” “includes,” and/or “including” when used herein, specifythe presence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

In the present application, the terms UE (User Equipment), terminal,mobile station, handset, wireless device etc. are used interchangeablyto denote a device that communicates with a wireless infrastructure. Theterm should not be construed as to mean any specific type of device, itapplies to them all, and the solutions described here are applicable toall devices that use methods according embodiments of the presentdisclosure. Similarly, a base-station is intended to denote the node inthe wireless infrastructure that communicates with the UE. Differentnames may be applicable, and the functionality of the base-station maybe distributed in various ways. For example, there could be a radio headimplementing (or carrying out) parts of the radio protocols and acentralized unit that implements (or carries out) other parts of theradio protocols. We will not distinguish such implementations here,instead the term base-station will refer to all alternativearchitectures that can implement (or is operable to carry out) someembodiments according to the present disclosure.

Furthermore, as used herein, a “radio node” is either a radio accessnode or a wireless device.

As used herein, a “radio access node” is any node in a radio accessnetwork of a cellular communications network that operates to wirelesslytransmit and/or receive signals. Some examples of a radio access nodeinclude, but are not limited to, a base station (e.g., an enhanced orevolved Node B (eNB) in a Third Generation Partnership Project (3GPP)Long Term Evolution (LTE) network or a gNB in a 3GPP New Radio (NR)network), a high-power or macro base station, a low-power base station(e.g., a micro base station, a pico base station, a home eNB, or thelike), and a relay node.

As used herein, a “core network node” is any type of node in a corenetwork. Some examples of a core network node include, e.g., a MobilityManagement Entity (MME), a Packet Data Network (PDN) Gateway (P-GW), aService Capability Exposure Function (SCEF), or the like.

As used herein, a “wireless device” is any type of device that hasaccess to (i.e., is served by) a cellular communications network bywirelessly transmitting and/or receiving signals to a radio accessnode(s). Some examples of a wireless device include, but are not limitedto, a User Equipment device (UE) in a 3GPP network and a Machine TypeCommunication (MTC) device.

As used herein, a “network node” is any node that is either part of theradio access network or the core network of a cellular communicationsnetwork/system.

Note that the description given herein focuses on a 3GPP cellularcommunications system and, as such, 3GPP LTE terminology or terminologysimilar to 3GPP LTE terminology is oftentimes used. However, theconcepts disclosed herein are not limited to LTE or a 3GPP system.

Note that, in the description herein, reference may be made to the term“cell;” however, particularly with respect to the Fifth Generation (5G),or NR's concepts, beams may be used instead of cells and, as such, it isimportant to note that the concepts described herein are equallyapplicable to both cells and beams. Throughout the disclosure, ‘downlink(DL)/uplink (UL) transmission’ refers to a communication link with atransmitter from one radio node and a receiver at another radio node. Inlegacy cellular systems, the functions of network node and UE node arenot symmetric, therefore there is DL or UL. For the sidelinkcommunications, two nodes (often both are UE devices) are symmetric byfunction. ‘Sidelink transmission (or communication)’ also refers to acommunication link with a transmitter from one node and a receiver atanother node.

Embodiments of the present disclosure for determining a transmissiondata block size potentially allow an easier evolution or changes of thesystem and/or improved performance.

FIG. 2 illustrates one example of a wireless communications system 10(e.g., a cellular network) in which embodiments of the presentdisclosure may be implemented. As illustrated, the wirelesscommunications system 10 includes a radio access node 12 that provideswireless, or radio, access to a wireless device 14. In some embodiments,the wireless communications system 10 is a 3GPP LTE network in whichcase the radio access node 12 may be an eNB (and thus referred to hereinas an eNB 12). In some other embodiments, the wireless communicationssystem 10 is a 3GPP NR network in which case the radio access node 12may be a gNB (and thus referred to therein as a gNB 12). Notably, forthe following description, the radio access node 12 is an eNB 12 and thewireless device 14 is a UE (and thus referred to herein as a UE 14);however, the present disclosure is not limited thereto.

In the present disclosure, the generic term transmission data block size(TDBS) is used. Such transmission data block size (TDBS) may correspondto the transport block size (TBS) as used in current LTE specifications.Such transmission data block size (TDBS) may also correspond todifferent protocol definitions and different aggregations of radioresource units. Non-limiting examples of radio resource units includeOFDM symbols, spatial layers, bandwidth parts and carriers. The term PRB(Physical Resource Block) is also used as a generic term to refer toresource allocation unit in a system operating based on variousprotocols, not only based on current LTE specifications. It will beclear to one skilled in the art to apply the teaching to these differentdefinitions or aggregation variations.

A flow chart illustrating a method 110 for a radio node according toembodiments of one aspect of the disclosure is illustrated in FIG. 3.The method 110 is for a radio node, for example wireless device 14. Themethod comprises the following steps:

Step 100 (optional): OBTAINING INFORMATION THAT ALLOWS TO DETERMINETDBS;

Step 104: DETERMINING TDBS, WHEREIN THE TDSB IS BASED, AT LEAST IN PART,ON AN EFFECTIVE NUMBER OF RESOURCE ELEMENTS, N_(RE);

Step 108 (optional): USING THE DETERMINED TDBS IN COMMUNICATION OVER ARADIO ACCESS LINK.

A flow chart illustrating a method 210 for a radio node according toembodiments of another aspect of the disclosure is illustrated in FIG.4. The method is for a radio node, for example network node 12. Themethod 210 comprises the following steps:

STEP 200-A: TRANSMITTING INFORMATION THAT ALLOWS A SECOND RADIO NODE TODETERMINE TDBS, THE TDBS BASED AT LEAST IN PART ON AN EFFECTIVE NUMBEROF RESOURCE ELEMENTS; AND/OR

STEP 200-B: CAUSING ANOTHER RADIO NODE TO TRANSMIT INFORMATION THATALLOWS A SECOND RADIO NODE TO DETERMINE TDBS, THE TDBS BASED AT LEAST INPART ON AN EFFECTIVE NUMBER OF RESOURCE ELEMENTS

Steps 200-A and 200-B, may both be performed, or only one may beperformed. If both are performed, the information transmitted in eachstep may be complementary.

Further embodiments, that may be used on their own or in combinationwith the methods in FIGS. 3 and 4, are described next.

Determination Using the Effective Number of Resource Elements per PRB(Method A)

In one aspect of the present disclosure, in a method (A) for a radionode such as a UE, the transmission data block size is determined usingthe effective number of resource elements per PRB. Throughout thepresent disclosure, PRB is used as the frequency domain unit of resourceallocation and has no limitation of the resource allocated in the timedomain.

According to one embodiment according to this aspect, the radio node(e.g. a UE) determines the transmission data block size based on amodulation order Q_(m), a code rate r, the number of spatial layers v,the allocated number of PRBs N_(PRB) and an effective number of resourceelements per PRB N_(RE).

In another nonlimiting embodiment, the transmission data block size isgiven by:

N_(PRB)·N_(RE) 19 v·Q_(m)·r  [1]

In another nonlimiting embodiment, the transmission data block size isadjusted to be aligned with a specific size unit C:

$\begin{matrix}{C \times \left\lceil \frac{N_{PRB} \cdot N_{RE} \cdot v \cdot Q_{m} \cdot r}{C} \right\rceil} & \lbrack 2\rbrack\end{matrix}$

where ┌x┐ is the ceiling function giving the smallest integer no smallerthan x. One nonlimiting example is C=8 such that the transmission datablock size is adjusted to be aligned with byte size:

$\begin{matrix}{8 \times \left\lceil \frac{N_{PRB} \cdot N_{RE} \cdot v \cdot Q_{m} \cdot r}{8} \right\rceil} & \lbrack 3\rbrack\end{matrix}$

Different settings of C allow the transmission data block size to beadjusted to satisfy different constraints. For example, in LTE, atransport block may be sub-divided into multiple code blocks withconstraint that all code blocks are of equal size. The same may beapplicable to other protocols.

In one embodiment, the parameters that are used to derive thetransmission data block size may be known to both the transmitter andthe receiver of a radio access link. In one embodiment, the parameters(or parameter values, or information related to the parameters) may besignaled between the transmitter and receiver either semi-statically,i.e. via higher layer signaling, or dynamically such as via physicalcontrol information (e.g. downlink control information (DCI)). Thesignaling of parameter values can be implicit (e.g. via otherparameters) or explicit (e.g. as standalone parameters). While othervariations are possible, one embodiment is described below:

-   -   Together the modulation order Q_(m) and code rate r are signaled        dynamically via DCI and are provided by one DCI field called MCS        (modulation and coding scheme). This is described with further        details below:    -   The number of spatial layers v is provided by a DCI field, e.g.        with the related MIMO scheme configured semi-statically via        higher layer signaling.    -   The number of allocated PRBs N_(PRB) is signaled dynamically by        a DCI field, or implied by PRB allocation which is also signaled        dynamically by a DCI field.    -   The effective number of resource elements per PRB N_(RE) can be        provided in multiple ways as described below:        -   i. Implicitly via other configuration parameters. For            example, the effective number of resource elements per PRB            can be determined by various configurations, including: the            slot configuration (including mini-slot), FDD vs TDD,            control region configuration, the reference symbol            configuration etc. In this case, no signaling of N_(RE) is            necessary. In some embodiments, the implicitly derived value            can also be considered the default value, which can be            overwritten by an explicitly signaled value.        -   ii. Explicitly via higher layer signaling. This is a            semi-static configuration of N_(RE). For example, the gNB            can select a value of N_(RE) from a set of predefined values            of N_(RE), and then send the selected value of N_(RE) to the            radio node (e.g. a UE) during RRC configuration or            reconfiguration. The selected value of N_(RE) is assumed by            both the transmitter and receiver for all subsequent            transmissions until a new value is signaled via higher layer            signaling.        -   iii. Explicitly via DCI. This is a dynamic configuration of            N_(RE). For example, the gNB can select a value of N_(RE)            from a set of predefined values of N_(RE), and then send the            selected value to the UE via a DCI field. In some            embodiments, the DCI signaled value is only used for the            data transmission related to the DCI, not for all the            subsequent transmissions. For DCI providing information for            a single data transmission, the value of N_(RE) may be used            for the single data transmission only. For DCI providing            information of semi-persistent data transmission, the value            of N_(RE) may be used for the multiple data transmission in            the semi-persistent configuration.        -   iv. A combination of the above methods. For example,            explicitly via a combination of higher layer signaling and            DCI signaling. This uses a combination of semi-static            configuration and dynamic configuration of N_(RE). A higher            layer signaling could be a base value, while an offset from            the base value could be signaled by the DCI.

In general, the aspects and their embodiments of the present disclosureare applicable for any radio access link between a transmitter and areceiver of two different radio nodes, respectively, including downlinkdata transmission, uplink data transmission and side-link communication.For the parameter N_(RE), according to some embodiments, there may beone for the downlink communication and another one for the uplinkcommunication. For example, one parameter N_(RE) ^(DL,PRB) is definedfor the downlink data transmission, while another parameter N_(RE)^(UL,PRB) is defined for the uplink data transmission. Typically, N_(RE)^(DL,PRB) and N_(RE) ^(UL,PRB) take independent and different values.

Furthermore, yet another parameter can be defined for the sidelinkcommunication. In this case, two peer devices can share a singlesidelink parameter N_(RE) ^(SL,PRB).

For HARQ transmission and retransmission of a same data block (e.g.,transport block, TB), the block size may have to be kept the same, evenwhen:

-   -   DCI of a transmission or retransmission is not received        correctly, including the initial transmission;    -   HARQ-ACK response to a transmission or retransmission is not        received correctly, including the initial transmission;    -   Time and/or frequency resource configuration changes between the        (re-)transmissions of a same data block.

Hence, the base station may have to make sure that when considering theaggregated effect of all the parameters, the transmission data blocksize (TDBS) obtained by embodiments of the above method stays the samefor a given transport block, even if individual parameter value maychange.

Signaling of MCS

It's one feature of some embodiments of the present disclosure that aradio node (e.g. a UE) use an MCS index I_(MCS) to determine themodulation order Q_(m) and code rate r. In one exemplary embodiment, theradio node (e.g. a UE) reads the modulation order Q_(m) and code rate rfrom an MCS table using the MCS index I_(MCS). A nonlimiting example ofthe MCS table is shown in Table 5.

It is noted that multiple MCS tables can be defined in the NR system.For example:

-   -   Downlink and uplink may have different MCS tables.    -   OFDM and DFT-S-OFDM based transmissions may use different MCS        tables;    -   Different radio node (e.g. UE) categories may use different MCS        tables. For example, low-cost UEs (e.g., MTC UE, NB-IoT UEs) may        use different MCS tables.

TABLE 1 Nonlimiting exemplary MCS table according to some embodiments ofthe disclosure MCS index Modulation order Code rate I_(MCS) Q_(m) r ×1024 0 2 120 1 2 157 2 2 193 3 2 251 4 2 308 5 2 379 6 2 449 7 2 526 8 2602 9 2 679 10 4 340 11 4 378 12 4 434 13 4 490 14 4 553 15 4 616 16 4658 17 6 438 18 6 466 19 6 517 20 6 567 21 6 616 22 6 666 23 6 719 24 6772 25 6 822 26 6 873 27 6 910 28 6 948

Signaling of the Effective Number of Resource Elements per PRB N_(RE)

It's a further feature of some embodiments according to the presentdisclosure that the effective number of resource elements per PRB N_(RE)is semi-statically configured by the network node (such as 12) viahigher layer signaling system. The effective number of resource elementsper PRB N_(RE) can be included in the system information blocktransmission or broadcast. The effective number of resource elements perPRB N_(RE) can be configured by higher protocols such as the radioresource control (RRC) layer protocol.

It's yet another feature of some embodiments according to the presentdisclosure that the network node 12, via higher layer signaling,semi-statically configures a set of values for the effective number ofresource elements per PRB N_(RE). An index may be included in thedownlink control information (DCI) to indicate the N_(RE) value that theradio node (e.g. UE) should apply to the corresponding transmission orreception. In one nonlimiting example, two N_(RE) values aresemi-statically configured and a 1-bit index is included in the DCI toselect the applicable N_(RE) value. In another nonlimiting example, fourN_(RE) values are semi-statically configured and a 2-bit index isincluded in the DCI to select the applicable N_(RE) value.

In a further embodiment, the effective one or multiple numbers ofresource elements per PRB N_(RE) are provided in the DCI.

Examples for calculating the effective number of resource elements perPRB N_(RE) are now provided.

One example of calculating N_(RE) for DL, N_(RE) ^(DL,PRB), is:

N _(RE) ^(DL,PRB)=12×n _(OFDM) −N _(RE) ^(PTRS)  [4]

Here n_(OFDM) is the number of OFDM symbols used for data transmission.Typical value of n_(OFDM) for a slot is n_(OFDM)=5 or n_(OFDM)=12, where2 OFDM symbols are excluded for DL control and DMRS. Lower values ofn_(OFDM) is expected when a mini-slot is used for data transmission.

N_(RE) ^(PTRS) is the average number of resource elements per PRB usedfor Phase Tracking Reference Signal (PTRS). In the above, 12 refers tothe number of subcarriers in a PRB, i.e. there are 12 subcarriers in aPRB in this example.

In one embodiment, if the slot configuration does not change between(re-)transmissions associated with the given transport block, theparameter N_(RE) ^(DL,PRB) may be calculated by:

N _(RE) ^(DL,PRB)=12×(N _(symb) ^((n) ^(sc) ⁾(n _(DataSlots)−1)+l_(DataStop) −l _(DataStart)+1)−N _(RE) ^(PTRS)  [5]

where n_(DataSlots), l_(DataStart), l_(DataStop) are defined as:

-   -   the length in number of slots of the resource allocation,        n_(DataSlots),    -   the first OFDM symbol in the first slot of the corresponding        PDSCH, l_(DataStart),    -   the last OFDM symbol in the last slot of the corresponding        PDSCH, l_(DataStop).    -   and N_(RE) ^(PTRS) is the average number of REs per PRB that is        used for PTRS.

Determination Using the Effective Number of Resource Elements perTime-Domain Symbol per PRB (Method B)

In another embodiment, in a method (B) for a radio node (e.g. either aUE or a base station), the transmission data block size is determinedusing the effective number of resource elements per time-domain symbolper PRB. The time-domain symbol can be either OFDM symbol or DFT-SC-OFDMsymbol, for an uplink transmission for example.

The UE determines the transmission data block size based on a modulationorder Q_(m), a code rate r, the number of spatial layers v, theallocated number of PRBs N_(PRB), the number of allocated time-domainsymbols (OFDM symbols or DFT-SOFDM symbols) N_(symb), and an effectivenumber of resource elements per OFDM symbol (or DFT-SC-OFDM symbol) perPRB N_(RE) ^(symb).

In one nonlimiting embodiment, the transmission data block size is givenby:

N_(PRB)·N_(symb)·N_(RE) ^(symb)·v·Q_(m)·r

In another nonlimiting embodiment, the transmission data block size isadjusted to be aligned with a specific size unit C:

$\begin{matrix}{C \times \left\lceil \frac{N_{PRB} \cdot N_{symb} \cdot N_{RE}^{symb} \cdot v \cdot Q_{m} \cdot r}{C} \right\rceil} & \lbrack 7\rbrack\end{matrix}$

where ┌x┐ is the ceiling function giving the smallest integer no smallerthan x. One nonlimiting example is C=8 such that the transmission datablock size is adjusted to be aligned with byte size:

$\begin{matrix}{8 \times \left\lceil \frac{N_{PRB} \cdot N_{symb} \cdot N_{RE}^{symb} \cdot v \cdot Q_{m} \cdot r}{8} \right\rceil} & \lbrack 8\rbrack\end{matrix}$

Different settings of C allow the transmission data block size to beadjusted to satisfy different constraints. For example, currently inLTE, a transport block may be sub-divided into multiple code blocks withthe constraint that all code blocks are of equal size.

Similar to some embodiments of the method (A), the parameters that areused to derive the transmission data block size are known to both thetransmitter and the receiver. The knowledge about the parameter valuesis signaled between the transmitter and receiver either semi-staticallyvia higher layer signaling, or dynamically via downlink controlinformation (DCI). The signaling of the parameter values can be implicitor explicit.

Similar to some embodiments of the method (A), the base station can makesure that when considering the aggregated effect of all parameters, thedata block size obtained by the above method stays the same for a giventransport block, even if individual parameter values may change.

An example for calculating the number of allocated time-domain symbolsN_(symb) is shown below.

For DL transmissions, the resource allocation in the time domain isgiven by:

-   -   the length in number of slots of the resource allocation,        n_(DataSlots),    -   the first OFDM symbol in the first slot of the corresponding        PDSCH, l_(DataStart),    -   the last OFDM symbol in the last slot of the corresponding        PDSCH, l_(DataStop).

Then,N_(symb)=#symbols_per_slot*#slots−#symbols_lost_at_start−#symbols_lost_at_end,i.e.:

N _(symb) =N _(symb) ^((n) ^(sc) ⁾ n _(DataSlots) −l _(DataStart)−(N_(symb) ^((n) ^(sc) ⁾ −l _(DataStop)−1)=N _(symb) ^((n) ^(sc) ⁾(n_(DataSlots)−1) +l _(DataStop) −l _(DataStart)+1  [9]

Examples of N_(RE) ^(symb) values are provided below.

If all REs in a time domain symbol per PRB is used for datatransmission, then N_(RE) ^(symb)=12.

If on average, d REs cannot be used for data transmission in a timedomain symbol per PRB, then N_(RE) ^(symb)=12−d.

Now, turning to FIG. 10, a method 300 in a user equipment (UE), such 14,for determining the TDBS will be described. Method 300 is an exampleembodiment of method 110.

Method 300 comprises the following steps:

Step 310: Obtaining parameters for a data transmission, the parametersincluding at least a number of layers, a number of allocated resourceblocks, a modulation order and a code rate.

Step 320: Determining an effective number of resource elements.

Step 330: Determining a transmission data block based on the obtainedparameters and the determined effective number of resource elements.

Step 340: Performing one of transmitting and receiving data based on thedetermined transmission data block size.

For example, in step 310, obtaining the parameters may comprisereceiving a signal comprising information (such as DCI) from a networknode, such as the gNB 12, the information related to the number oflayers, the modulation order and the code rate and the number ofallocated resource blocks. For example, the DCI may comprise a firstfield such as the MCS field for indicating the modulation order and thecode rate, a second field for indicating the number of layers, and athird field (such as a resource allocation field) for indicating thenumber of allocated PRBs. The MCS field may comprise a MCS index, whichcan be used by the UE to look up a MCS table to determine the modulationorder and code rate. In some embodiments, the signal or DCI may compriseinformation related to the modulation order and the code rate and thenumber of allocated resource blocks. The number of layers can bepredefined or configured. In some embodiments, the signal may be asignaling of higher layer than the physical layer. For example, thesignal can be a RRC signal, which comprises the information related tothe parameters.

In step 320, the effective number of resource elements N_(RE) can bedetermined in different ways. It should be noted that the effectivenumber of resource elements represent the number of REs which areexclusively used for carrying user data (i.e. no control data).

For example, the determination of the effective number of resourceelements can be based at least on one or more of: a slot configuration,mini-slot configuration, control region configuration, reference symbolconfiguration, frequency division duplex and time division duplex.

In some embodiments, the gNB can select a value of N_(RE) from a set ofpredefined values of N_(RE) and then send the selected value to the UE.As such, the UE receives the N_(RE) via higher layer signaling, forexample, during a RRC configuration. The gNB can also send the selectedvalue of N_(RE) via DCI. In some embodiments, the UE can determine aneffective number of resource elements for an uplink transmission, adownlink transmission or a sidelink transmission. An example of theeffective number of resource elements for the downlink transmission(N_(RE) ^(DL,PRB)) can be determined as follows:

N _(RE) ^(DL,PRB)=12×n _(OFDM) −N _(RE) ^(PTRS)

where n_(OFDM) is a number of OFDM symbols used for the datatransmission, N_(RE) ^(PTRS) is an average number of resource elementsper PRB used for Phase Tracking Reference Signal (PTRS), 12 refers tothe number of subcarriers in a PRB.

In step 330, the UE can determine the TDBS based on the obtainedparameters and the determined effective number of resource elements asfollows:

N_(PRB)·N_(RE)·v·Q_(m)·r

where N_(PRB) is the number of allocated resource blocks, N_(RE) is thenumber of effective resource elements, v is the number of layers, Q_(m)is the modulation order and r is the code rate.

In some embodiments, the UE may further adjust the determined TDBS to bealigned with a size unit, such as C. As such, the adjusted TDBS is ableto satisfy different constraints, imposed by the size C, for example.

To do so, the UE may determine the adjusted TDBS as follows:

$C \times \left\lceil \frac{N_{PRB} \cdot N_{RE} \cdot v \cdot Q_{m} \cdot r}{C} \right\rceil$

It should be noted that the effective number of resource elements cancomprise an effective number of resource elements per PRB or aneffective number of resource elements per time domain symbol per PRB.For example, the time-domain symbol can be an OFDM symbol or aDFT-SC-OFDM symbol. In this case, the TDBS can be given by equation [6]and the adjusted TDBS to align with the size C can be given by equation[7].

In step 340, once the TDB S is determined, the UE can either transmitdata or receive data, based on the determined TDBS.

FIG. 11 illustrates a flow chart of a method 400 for receiving ortransmitting data. Method 400 is an example of method 210 of FIG. 4.Method 400 can be implemented in the network 12, for example.

Method 400 comprises the following steps.

Step 410: transmitting parameters for a data transmission, theparameters including at least a number of layers, a number of allocatedresource blocks, a modulation and a code rate.

Step 420: transmitting an effective number of resource elements.

step 430: performing one of receiving and transmitting data based on atransmission data block size, which is determined based on thetransmitted parameters and effective number of resource elements.

For example, in step 410, the network node can transmit the parametersfor the data transmission in a signal comprising information such asDCI. The DCI may comprise different fields for indicating theparameters. For example, the DCI may have a MCS field for indicating themodulation order and code rate, a resource allocation field forindicating the number of allocated PRBs and a field for indicating thenumber of layers. In some embodiments, the signal or DCI may compriseinformation related to the modulation order and code rate and the numberof allocated PRBs. The number of layers can be predefined or configured.In some embodiments, the network node can transmit the parameters usinghigher layer signaling, such as a RRC signal.

In step 420, the network node can first determine the effective numberof resource elements (N_(RE)) before sending it. For example, thenetwork node can determine N_(RE) based on at least on one or more of: aslot configuration, mini-slot configuration, control regionconfiguration, reference symbol configuration, frequency division duplexand time division duplex. The network node can also select a N_(RE)value among a set of predefined effective number of resource elementsand then send the selected N_(RE) to the UE.

Furthermore, the effective number of resource elements can betransmitted to the UE in a signal comprising DCI or through higher layersignaling such as a RRC signal.

In step 430, the network node can either transmit data or receive data,based on a determined TDBS. The TDBS can be determined by the networknode itself or it can be received from the UE or even from another node.

FIG. 5 is a schematic block diagram of the wireless device 14 accordingto some embodiments of the present disclosure. As illustrated, thewireless device 14 includes circuitry 16 comprising one or moreprocessors 18 (e.g., Central Processing Units (CPUs), ApplicationSpecific Integrated Circuits (ASICs), Field Programmable Gate Arrays(FPGAs), and/or the like) and memory 20. The wireless device 14 alsoincludes one or more transceivers 22 each including one or moretransmitter 24 and one or more receivers 26 coupled to one or moreantennas 28. In some embodiments, the functionality of the wirelessdevice 14 described above may be fully or partially implemented insoftware that is, e.g., stored in the memory 20 and executed by theprocessor(s) 18. For example, the processor 18 is configured to performmethod 110 of FIG. 3 and method 300 of FIG. 10.

In some embodiments, a computer program including instructions which,when executed by the at least one processor 18, causes the at least oneprocessor 18 to carry out the functionality of the wireless device 14according to any of the embodiments described herein is provided (e.g.methods 110 and 300). In some embodiments, a carrier containing theaforementioned computer program product is provided. The carrier is oneof an electronic signal, an optical signal, a radio signal, or acomputer readable storage medium (e.g., a non-transitory computerreadable medium such as memory).

FIG. 6 is a schematic block diagram of the wireless device 14 accordingto some other embodiments of the present disclosure. The wireless device14 includes one or more modules 30, each of which is implemented insoftware. The module(s) 30 provide the functionality of the wirelessdevice 14 described herein. The module(s) 30 may comprise, for example,an obtaining module operable to perform steps 100 of FIG. 3 and 310 ofFIG. 10, a determination module operable to perform steps 104 of FIG. 3and 320 and 330 of FIG. 10, and a use module operable to perform step108 of FIG. 3 or a transmitting/receiving module operable to performstep 340 of FIG. 10.

FIG. 7 is a schematic block diagram of a network node 32 (e.g., a radioaccess node 12) according to some embodiments of the present disclosure.As illustrated, the network node 32 includes a control system 34 thatincludes circuitry comprising one or more processors 36 (e.g., CPUs,ASICs, FPGAs, and/or the like) and memory 38. The control system 34 alsoincludes a network interface 40. In embodiments in which the networknode 32 is a radio access node 12, the network node 32 also includes oneor more radio units 42 that each include one or more transmitters 44 andone or more receivers 46 coupled to one or more antennas 48. In someembodiments, the functionality of the network node 32 described abovemay be fully or partially implemented in software that is, e.g., storedin the memory 38 and executed by the processor(s) 36. For example, theprocessor 36 can be configured to perform the methods 210 of FIG. 4 and400 of FIG. 11.

FIG. 8 is a schematic block diagram of the network node 32 (e.g., theradio access node 12) according to some other embodiments of the presentdisclosure. The network node 32 includes one or more modules 62, each ofwhich is implemented in software. The module(s) 62 provide thefunctionality of the network node 32 described herein. The module(s) 62may comprise a transmitting module operable to transmit or cause anothernode to transmit to a wireless device 14 information that allowsdetermining a TDBS, as per steps 200-A and 200-B of FIG. 4. Thetransmitting module may also be operable to perform the steps 410 and420 of FIG. 11. The modules 62 may further comprise areceiving/transmitting module operable to perform step 430 of FIG. 11.

FIG. 9 is a schematic block diagram that illustrates a virtualizedembodiment of the network node 32 (e.g., the radio access node 12)according to some embodiments of the present disclosure. As used herein,a “virtualized” network node 32 is a network node 32 in which at least aportion of the functionality of the network node 32 is implemented as avirtual component (e.g., via a virtual machine(s) executing on aphysical processing node(s) in a network(s)). As illustrated, thenetwork node 32 optionally includes the control system 34, as describedwith respect to FIG. 10. In addition, if the network node 32 is theradio access node 12, the network node 32 also includes the one or moreradio units 42, as described with respect to FIG. 10. The control system34 (if present) is connected to one or more processing nodes 50 coupledto or included as part of a network(s) 52 via the network interface 40.Alternatively, if the control system 34 is not present, the one or moreradio units 42 (if present) are connected to the one or more processingnodes 50 via a network interface(s). Alternatively, all of thefunctionality of the network node 32 described herein may be implementedin the processing nodes 50 (i.e., the network node 32 does not includethe control system 34 or the radio unit(s) 42). Each processing node 50includes one or more processors 54 (e.g., CPUs, ASICs, FPGAs, and/or thelike), memory 56, and a network interface 58.

In this example, functions 60 of the network node 32 described hereinare implemented at the one or more processing nodes 50 or distributedacross the control system 34 (if present) and the one or more processingnodes 50 in any desired manner. In some particular embodiments, some orall of the functions 60 of the network node 32 described herein areimplemented as virtual components executed by one or more virtualmachines implemented in a virtual environment(s) hosted by theprocessing node(s) 50. As will be appreciated by one of ordinary skillin the art, additional signaling or communication between the processingnode(s) 50 and the control system 34 (if present) or alternatively theradio unit(s) 42 (if present) is used in order to carry out at leastsome of the desired functions. Notably, in some embodiments, the controlsystem 34 may not be included, in which case the radio unit(s) 42 (ifpresent) communicates directly with the processing node(s) 50 via anappropriate network interface(s).

In some embodiments, a computer program including instructions which,when executed by the at least one processor 36, 54, causes the at leastone processor 36, 54 to carry out the functionality of the network node32 or a processing node 50 according to any of the embodiments describedherein is provided. In some embodiments, a carrier containing theaforementioned computer program product is provided. The carrier is oneof an electronic signal, an optical signal, a radio signal, or acomputer readable storage medium (e.g., a non-transitory computerreadable medium such as the memory 56.

The above described embodiments are intended to be examples only.Alterations, modifications and variations may be effected to theparticular embodiments by those of skilled in the art without departingfrom the scope of the description, which is defined by the appendedclaims.

ABBREVIATIONS

The present description may comprise one or more of the followingabbreviations:

-   -   3GPP Third Generation Partnership Project    -   5G Fifth Generation    -   ACK Acknowledgement    -   ASIC Application Specific Integrated Circuit    -   CC Chase Combining    -   CPU Central Processing Unit    -   CRC Cyclic Redundancy Check    -   DCI Downlink Control Information    -   DFT-SC-OFDM Discrete Fourier Transform Single Carrier Orthogonal        Frequency Division Multiplexing    -   eMBB Enhanced Mobile Broadband    -   eNB Enhanced or Evolved Node B    -   FPGA Field Programmable Gate Array    -   gNB Base station in 5G network    -   HARQ Hybrid Automatic Repeat Request    -   IR Incremental Redundancy    -   LDPC Low-Density Parity-Check    -   LTE Long Term Evolution    -   MCS Modulation and Coding Scheme    -   MME Mobility Management Entity    -   MTC Machine Type Communication    -   NACK Negative Acknowledgement    -   NDI New Data Indicator    -   NR New Radio    -   OFDM Orthogonal Frequency Division Multiplexing    -   PDCCH Physical Downlink Control Channel    -   PDN Packet Data Network    -   PDSCH Physical Downlink Shared Channel    -   P-GW Packet Data Network Gateway    -   RV Redundancy Version    -   SCEF Service Capability Exposure Function    -   SRS Sounding Reference Signal    -   TRP Transmission-Receive-Point    -   UE User Equipment    -   URLLC Ultra-Reliable and Low-Latency Communications

What is claimed is:
 1. A method in a User Equipment (UE), the methodcomprising: obtaining parameters for a data transmission, the parametersincluding at least a number of layers, a number of allocated resourceblocks, a modulation order and a code rate; determining an effectivenumber of resource elements; determining a transmission data block size(TDBS) based on the obtained parameters and the determined effectivenumber of resource elements; and performing one of transmitting andreceiving data based on the determined transmission data block size. 2.The method of claim 1, wherein obtaining the parameters comprisesreceiving from a network node a signal comprising information related tothe number of layers, the modulation order and the code rate and thenumber of allocated resource blocks.
 3. The method of claim 1, whereindetermining the effective number of resource elements is based at leaston one or more of: a slot configuration, mini-slot configuration,control region configuration, reference symbol configuration, frequencydivision duplex and time division duplex.
 4. The method of claim 1,wherein determining the effective number of resource elements comprisesreceiving, from a network node, an effective number of resource elementsselected from a set of predefined effective numbers of resource elementsby the network node.
 5. The method of claim 4, wherein the selectedeffective number of resource elements is received via DCI.
 6. The methodof claim 1, wherein determining the effective number of resourceelements comprises determining one or more of: a first effective numberof resource elements for an uplink transmission, a second effectivenumber of resource elements for a downlink transmission and a thirdnumber of resource elements for a sidelink transmission.
 7. The methodof claim 6, wherein determining the effective number of resourceelements for the downlink transmission (N_(RE) ^(DL,PRB)) comprisescalculating:N _(RE) ^(DL,PRB)=12×n _(OFDM) −N _(RE) ^(PTRS) where n_(OFDM) is anumber of OFDM symbols used for the data transmission, N_(RE) ^(PTRS) isan average number of resource elements per PRB used for Phase TrackingReference Signal (PTRS), 12 refers to a number of subcarriers in a PRB.8. The method of claim 1, wherein determining the transmission datablock size based on the obtained parameters and the determined effectivenumber of resource elements comprises calculating:N_(PRB)·N_(RE)·v·Q_(m)·r where N_(PRB) is the number of allocatedresource blocks, N_(RE) is the number of effective resource elements, vis the number of layers, Q_(m) is the modulation order and r is the coderate.
 9. The method of claim 1, further comprising adjusting thedetermined TDBS to be aligned with a size unit C, wherein adjusting thedetermined TDBS to be aligned with the size unit C comprisescalculating:$C \times \left\lceil \frac{N_{PRB} \cdot N_{RE} \cdot v \cdot Q_{m} \cdot r}{C} \right\rceil$where N_(PRB) is the number of allocated resource blocks, N_(RE) is thenumber of effective resource elements, v is the number of layers, Q_(m)is the modulation order and r is the code rate, and ┌ ┐ is a ceilingfunction.
 10. The method of claim 9, wherein the size unit C is used toadjust the TDBS so that all code blocks are of equal size when thetransmission data block is sub-divided into multiple code blocks. 11.The method of claim 1, wherein the effective number of resource elementscomprises a number of resource elements per physical resource block(PRB).
 12. A User Equipment (UE) comprising a network interface and aprocessing circuitry connected thereto, the processing circuitrycomprising a processor and a memory connected thereto, the memorycontaining instructions that, when executed, cause the processor to:obtain parameters for a data transmission, the parameters including atleast a number of layers, a number of allocated resource blocks, amodulation order and a code rate; determine an effective number ofresource elements; determine a transmission data block size (TDBS) basedon the obtained parameters and the determined effective number ofresource elements; and perform one of transmit and receive data based onthe determined transmission data block size.
 13. The UE of claim 12,wherein the processor is further configured to receive from a networknode a signal comprising information related to the number of layers,the modulation order and the code rate and the number of allocatedresource blocks.
 14. The UE of claim 13, wherein the informationcomprises Downlink Control information (DCI) and wherein the DCIcomprises a Modulation Coding Scheme (MCS) field for indicating themodulation order and the code rate and wherein the MCS field comprises aMCS index, which is used by the UE to look up a MCS table to determinethe modulation order and code rate.
 15. The UE of claim 12, wherein theprocessor is further configured to determine the effective number ofresource elements based at least on one or more of: a slotconfiguration, mini-slot configuration, control region configuration,reference symbol configuration, frequency division duplex and timedivision duplex.
 16. The UE of claim 12, wherein the processor isfurther configured to receive, from a network node, an effective numberof resource elements selected from a set of predefined effective numbersof resource elements.
 17. The UE of claim 16, wherein the processor isfurther configured to receive the selected effective number of resourceelements via DCI.
 18. The UE of claim 12, wherein the processor isfurther configured to determine one or more of: a first effective numberof resource elements for an uplink transmission, a second effectivenumber of resource elements for a downlink transmission and a thirdnumber of resource elements for a sidelink transmission.
 19. The UE ofclaim 18, wherein the processor is further configured to determine theeffective number of resource elements for the downlink transmission(N_(RE) ^(DL,PRB)) by calculating:N _(RE) ^(DL,PRB)=12×n _(OFDM) −N _(RE) ^(PTRS) where n_(OFDM) is anumber of OFDM symbols used for the data transmission, N_(RE) ^(PTRS) isan average number of resource elements per PRB used for Phase TrackingReference Signal (PTRS), 12 refers to a number of subcarriers in a PRB.20. The UE of claim 12, wherein the processor is further configured todetermine the transmission data block size based on the obtainedparameters and the determined effective number of resource elements bycalculating:N_(PRB)·N_(RE)·v·Q_(m)·r where N_(PRB) is the number of allocatedresource blocks, N_(RE) is the number of effective resource elements, vis the number of layers, Q_(m) is the modulation order and r is the coderate.
 21. The UE of claim 12, wherein the processor is furtherconfigured to adjust the determined TDBS to be aligned with a size unit.22. The UE of claim 21, wherein the processor is further configured toadjust the determined TDBS to be aligned with a size unit C bycalculating:$C \times \left\lceil \frac{N_{PRB} \cdot N_{RE} \cdot v \cdot Q_{m} \cdot r}{C} \right\rceil$where N_(PRB) is the number of allocated resource blocks, N_(RE) is thenumber of effective resource elements, v is the number of layers, Q_(m)is the modulation order and r is the code rate, and ┌ ┐ is a ceilingfunction.
 23. The UE of claim 22, wherein the size unit C is used toadjust the TDBS so that all code blocks are of equal size when thetransport data block is sub-divided into multiple code blocks.
 24. TheUE of claim 12, wherein the effective number of resource elementscomprises an effective number of resource elements per physical resourceblock (PRB).
 25. The UE of claim 12, wherein the processor is furtherconfigured to determine an effective number of resource elements pertime-domain symbol per PRB.
 26. The UE of claim 25, wherein theprocessor is further configured to determine the transmission data blocksize based on the obtained parameters and the determined effectivenumber of resource elements by calculating:N_(PRB)·N_(symb)·N_(RE) ^(symb)·v·Q_(m)·r where N_(PRB) is the number ofallocated resource blocks, N_(RE) ^(symb) is the number of effectiveresource elements per symbol per PRB, v is the number of layers, Q_(m)is the modulation order, r is the code rate and N_(symb) is a number ofallocated time-domain symbols.
 27. The UE of claim 26, wherein theprocessor is further configured to adapt the determined TDBS to bealigned with a size unit.
 28. The UE of claim 12, wherein the processoris further configured to receive from a network node a signal comprisinginformation related to the modulation order and the code rate and thenumber of allocated resource blocks and wherein the number of layers ispredefined.
 29. A network node comprising a network interface and aprocessing circuitry connected thereto, the processing circuitryconfigured to: transmit parameters for a data transmission, theparameters including a number of layers, a number of allocated resourceblocks, a modulation order and a code rate; transmit an effective numberof resource elements; and perform one of receive and transmit data basedon a transmission data block size, which is determined based on thetransmitted parameters and effective number of resource elements. 30.The network node of claim 29, wherein the processor is configured toselect an effective number of resource elements from a set of predefinedeffective number of resource elements prior to transmitting theeffective number of resource elements.